home *** CD-ROM | disk | FTP | other *** search
- Problems with specific applications
- -----------------------------------
-
- Crashes on 060 systems should no longer appear - if the library crashes
- on specific modules at startup-time, please trace it back with SnoopDOS,
- delete that specific modules, and contact me for a bug-report.
-
- Minor problems:
-
- o The combination superview.library / PMPro
- and MCP with active NEWTOOLTYPES patch did cause crashing the library
- at startup time. So don't use that patch...
-
- There seem to be more options in MCP, which may become 'critical'...
-
- Whenever you encounter any problems: first try it again without
- any patches running !
-
- o Do no mix libraries from Picasso96 and CyberGraphX - when again
- switching from P96 to CGfx with Picasso96API.library still being
- in LIBS: then your system will immediately crash with the next
- opening of that library.
-
-
- Here's a list of several programs, which either cause SuperView-Library
- to crash, or which may crash or fail unexpected (so that it might seem,
- as if SuperView-Library did crash or were the reason of the fault):
-
- o Mixed Picasso96 and CyberGfx environment
- ========================================
- Problem
- -------
- Picasso96 users, which have the Picasso96.svdriver installed
- (that's default, unless you "exclude" it via SVPrefs or
- delete it), and do switch between P96 and CyberGfx, should
- not the following: without removing Picasso96API.library
- from Libs: when CyberGfx is running, any program that
- tries to open Picasso96API.library will make it crashing
- (since that library tries to create another, emulated
- instance of cybergraphics.library, which must fail).
-
- Solution
- --------
- Either
-
- - delete/exclude Picasso96.svdriver
- - move all libraries, not only the monitor drivers,
- when switching between P96 and CyberGfx
- - wait for a bugfix (Tobias Abt and Frank Mariak
- both have been informed)
-
- o EGS libraries V6 and V7 © VIONA Development
- ===========================================
- Problem
- -------
- When flushing the EGS libraries, it seems that the libraries will
- cause recoverable alerts with OS 3.x.
- Maybe on some systems real crashes will occur.
- Don't know, whether the libraries are really the source,
- but it's likely.
-
- Solution
- --------
- Don't flush ;-)
-
- o DOpus5 (supposed to be fixed with Magellan release)
- ===================================================
- Problem
- -------
- Not a serious problem. DOpus5 does not seem to figure the correct
- version numbers from sv library files, when requested to do so.
-
- Solution
- --------
- C:Version libraryname
-
- o LX/020 1.03 © 1993 Xenomiga Technologie (Jonathan Forbes)
- =========================================================
- Problem
- -------
- Obviously can't correctly extract large LZH/LHA archives.
-
- o NewMode V3.3 (and below) © 1992-95 by Andreas Linnemann
- =========================================================
- Problem
- -------
- Has been reported to cause serious problems when running together
- with e.g. SuperView (when attaching a fixed ViewMode to the program).
-
- Solution
- --------
- Already fixed for newer versions.
- I, personally, would strongly recommend not to promote any SuperView
- Screens via NewMode, since now for almost any configuration there
- should be suitable SVDrivers - alternatively also a RTG-configuration
- for AGA.svdriver.
-
- o VMM (supposed to be fixed)
- ==========================
- Former versions of SuperView-Library did allocate all buffers
- with the MEMF_PUBLIC flag set, which prevented e.g. VMM
- from storing these as virtual memory on disk.
-
- As with current versions, the large image buffers - where
- it makes sense - are no longer prevented from being accessing
- by VMM. MEMF_PUBLIC no longer is set for these.
-
- Before - and with old modules - this could have been by-passed
- by setting the 10240 flag value within VMM's advanced options
- - but this should not be done any longer, since it may become
- dangerous under certain circumstances.
-
- o SnoopDOS
- ========
- Problem
- -------
- Some external libraries (being opened by SV modules) seem not
- to be snoop'able without causing crashes, then.
-
- Solution
- --------
- Turn off SnoopDOS.
-
-
-
-